I'm trying to deploy a windows 8.1 64bit image to a Microsoft Surface Pro 3 using WDS.

I am able to pxe boot the device to a certain point and this error appears. I use the USB Ethernet adapter from MS.

I have added the whole Surface driver pack into my deployment share downloaded from here
https://www.microsoft.com/en-us/download/details.aspx?id=38826I

I used this guide
http://blogs.technet.com/b/askcore/archive/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit.aspx

Can Anyone  point me to the right direction?

thanks,

Ron

• Edited by RonGielgens 22 hours 44 minutes ago typo's

PCI\VEN_11AB&DEV_2B38  = the WiFi adaptor... this isn't what you need for WinPE/PXE.. seems you have other issues (like, why it isn't trying the wired USB adaptor)

Steps #3,4,5,12 are the likely areas to focus on - these are where you prepare the drivers for WinPE and, generate the revised WinPE boot image, and then import the new boot image to your WDS (so you can PXE-boot).

If you don't have the correct Ethernet driver injected into your boot WIM, you will have exactly your problem.

The download file you need, to get the full driver set for all component devices, is currently named: SurfacePro3_150623
It's available here: http://www.microsoft.com/en-us/download/details.aspx?id=38826

It expands out to:

\SurfacePro3_150623\Drivers\Network\SurfaceEthernetAdapter\
\SurfacePro3_150623\Drivers\Network\SurfaceGigabitEthernetAdapter\
etc
[these are currently the same as in the zip files: Surface Ethernet Adapter.zip & Surface Gigabit Ethernet Adapter.zip]

Here's another guide, in case you're new to MDT:
https://www.microsoft.com/en-au/download/details.aspx?id=452

Hi Don,

thanks for your reply,

Yes, it seems to want to use the wifi drivers to continue, i injected them also, several times.
I did it again with the SurfacePro3_150623 drivers but still the same.

I am not so new to MDT, other system boot and deploy without problems, only the surface pro gives me a headache.

I going to continue troubleshooting, following your suggestion about preparing the drivers for WinPE, maybe i missed something.